Skip to main content

Implementing an effective data model

2 Tasks

45 mins

Visible to: All users
Advanced Pega Platform '23 English

Scenario

The Delivery Service team is currently in the design phase of their project and their first task is to review the current set of enterprise-level data classes developed by the MDC Center of Excellence (COE) team. The goal of this task is to identify which data classes the Delivery Service team can reuse in their design. During their analysis, the Delivery Service team may discover data classes that the MDC COE team has not defined. 
 
In such cases, the Delivery Service team must decide whether those undefined data classes are worthy of being defined at the enterprise level or, instead, be owned by the Delivery Service team. This decision should be based on factors such as the scope of the data class, its potential reuse across the enterprise, and the level of effort required to define and maintain the data class.
 
If the data class is deemed to have enterprise-level significance, the Delivery Service team should work with the MDC COE team to define the data class and ensure that it is added to the enterprise-level data model. On the other hand, if the data class is specific to the Delivery Service team's project, it should be owned by the Delivery Service team and defined as part of their project's data model. 
 
Overall, the Delivery Service team's analysis of the enterprise-level data classes developed by the MDC COE team is an important step in ensuring that their project is aligned with the enterprise-level data model and that data is managed consistently across the organization. 

The following table provides the credentials you need to complete the challenge:

Role User name Password
Administrator Admin@MDC rules

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Analyze the MDC enterprise data model

MDC-Data-model
  • A business partner has a contact, addresses, and an invoice. 
  • A truck vendor has a contact, addresses, truck service, and a truck. 
  • A delivery request has a pickup, delivery address, and an invoice. 
  • A truck request has an invoice.  
  • An invoice has a contact associated with it.
Class Description
MDC-Data-Contact Contact of Business partner, Vendor
MDC-Data-Address Address of Business partner, Vendor, Pickup, and delivery addresses are stored in this data type

MDC-Data-BusinessPartner

Holds the business partner data
MDC-Data-Invoice All the invoices paid and received
MDC-Data-TruckVendor Holds Truck Vendor data
MDC-Data-TruckService For each city how many trucks are being supplied for a given city where MDC operates, Type of contract, minimum trucks
MDC-Data-Truck Truck and its associated VIN, Size
MDC-Data-LinkDeliveryTruck A Delivery request can have more than 1 truck, as well a given truck can have delivery requests associated from various business partners. It is a many to many relation between Truck request and Delivery request.
CasesvsData

 

Case Associated Data Object Comments
Partner
  • Business partner
  • Contact
  • Addresses
  • Invoice
Case for Registration of partner with MDC
Vendor enrollment
  • Truck Vendor
  • Truck Service
  • Truck

Case for enrollment of Vendor with MDC

Truck service approval
  • Truck Service
  • Truck
Child case to vendor enrollment for parallel approvals from city managers
Delivery request
  • Delivery request
  • Addresses
  • Invoice
Case for Delivery request by business partner
Truck request
  • Truck request
  • Invoice
Case to track the delivery of the shipping orders from pickup to delivery address within the given city
Invoice
  • Invoice
Invoice to handle credits and debits.

2 Complete the following assignments

The data model's definition here includes the data model for each case type, not just Data- class-extending data types.

For each data model class, you must show:

  • The full class name and what class is extended
  • Whether the class is abstract or concrete
    • If concrete, the class shows the schema in which instances are persisted
  • Properties used for data relationships
    • Say embedded or, if a reference. add Ref to the property name
    • Say list if something is a list
  • Critical scalar properties
Note: An Interaction Diagram can help to gain a better perspective of the problem domain, especially the timing of inputs received by the system.

Confirm your work

      



Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice